|
All aeronautical telecommunication and navigation services in Finland are administered by Fintraffic ANS.
|
|
Fintraffic ANS
PL 157 FI-01531 VANTAA AFS: EFHKYAYA TEL: +358 20 428 4814 E-mail: aftn@ops-ansfinland.fi |
|
In the communication Procedures the following ICAO Documents are applicable:
|
|
Significant differences between national and international rules and procedures are given in section GEN 1.7.
|
|
The airspace within the Finnish flight information region (HELSINKI FIR, EFIN).
|
|
The following radio and radar aids to navigation are available:
|
|
Non-directional Radio Beacon (NDB)
Locator (L) En-route Surveillance Radar (RSR) Terminal Area Surveillance Radar (TAR) Instrument Landing System (ILS) VHF Omnidirectional Radio Range (VOR) Distance Measuring Equipment (DME) |
|
3.2.1. Mobile service
|
|
The aeronautical stations maintain a continuous watch on their designated frequencies during the published hours of service unless otherwise notified.
|
|
An aircraft should normally communicate with the Air Traffic Service unit which exercises control in the airspace in which the aircraft is flying.
|
|
The languages normally used in air-ground communications are Finnish and English.
|
|
3.2.2. Fixed Services (AFS)
|
|
Aerodomes are connected to each other through FASTNET which is maintained by Fintraffic ANS.
|
|
Additionally the COM Centre is provided with the following international connections:
|
|
EFHK - ULLL (Sankt-Peterburg) 128 kB CIDIN
EFHK - EKCH (Copenhagen) 64 kB AMHS EFHK - ESSS (Stockholm) 64 kB AMHS EFHK - EETN (Tallinn) 64 kB AMHS EFHK - EUCH (Eurocontrol NM Haren) 64 kB AMHS EFHK - EUCB (Eurocontrol NM Bretigny) 64 kB AMHS EFHK - EDDD (Frankfurt) 64 kB AMHS EFHK - EGGG (UK) 64 kB AMHS |
|
Messages to be transmitted over the Aeronautical Fixed Services are accepted only if
|
|
The direct international telephone lines from Helsinki ACC are as follows:
|
|
EFIN - ESOS (Stockholm ACC)
EFIN - ULLL (Sankt-Peterburg ACC) EFIN - EETT (Tallinn ACC) EFIN - EETN (Tallinn APP) EFIN - ESMM (Malmö ACC) EFIN - ULPP (Petrozavodsk ACC) EFIN - ENBD (Bodö ATCC) EFIN - ULMM (Murmansk ACC) |
|
The following RTF broadcasts are available for aircraft:
|
|
3.3.1. Automatic Terminal Information Service (ATIS)
|
|
ATIS broadcast consists of following elements according to ICAO Annex 11, chapter 4.3.7:
|
|
Note: At AFIS aerodrome 'runway in use' means 'preferred runway', see GEN 3.3 para 3.1.3.2. The pilot-in-command may use, traffic situation and prevailing circumstances permitting, other than preferred runway after reporting this to the AFIS unit.
|
|
Each broadcast is initiated by an alphabetic identification. Pilots are requested to listen to the broadcast prior to departure and before entering FIZ, TMA or CTR concerned and to report the identification letter of the broadcast received to the appropriate ATS unit at the beginning of the initial radio contact. If receipt of last broadcast has been acknowledged, the information contained therein will not be repeated by the ATS unit.
|
|
In case weather and runway conditions are changing rapidly, deviating significantly from information given in ATIS broadcast, the relevant MET and runway condition information will be communicated by the aerodrome ATS unit during its operational hours.
|
|
The frequencies and operation hours of ATIS broadcasts as well as local restrictions (EFHK) are given in part AD 2.
|
|
3.3.2. Languages used are Finnish and / or English.
|
|
3.3.3. Data link automatic terminal information service (D-ATIS)
|
|
Aircraft are allowed to receive ATIS and VOLMET via data link. This service operates through ACARS network and supports aircraft equipped with ACARS which is ARINC 622/623 compliant.
|
|
D-ATIS is available at the aerodromes as follows:
|
|
ATIS: EFET, EFHK, EFIV, EFJO, EFJY, EFKE, EFKI, EFKK, EFKS,
EFKT, EFKU, EFLP, EFMA, EFOU, EFPO, EFRO, EFSA, EFSI, EFTP, EFTU, EFVA |
|
D-ATIS being an additional service, no NOTAM concerning possible interruptions will be published.
|
|
Details of the various facilities available for the en-route traffic can be found in ENR 4. Details of the facilities available at the individual aerodromes can be found in AD 2. In cases where a facility is serving both the en-route traffic and the aerodromes, details are given in the relevant sections of ENR 4 and AD 2.
|
|
NIL
|
|
CPDLC services are available for aircraft operating within the airspace of HELSINKI FIR between FL95 and FL660, excluding ATS delegated areas HALTI CTA, MANTO CTA and KVARKEN CTA.
|
|
The following CPDLC services are provided in this airspace:
|
|
CPDLC Logon is mandatory for all capable and eligible flights in the airspace of HELSINKI FIR. Use of CPDLC in HELSINKI FIR is conducted at the discretion of ATC. Voice shall remain the primary means of communication in time-critical situations.
|
|
CPDLC messages shall be answered with the least possible delay. If required, e.g. due to the downlink request message having exceeded its time limit, the pilot shall repeat the request via radiotelephony.
|
|
Voice read-back is not required for any CPDLC clearance or instruction.
|
|
Pilots intending to conduct CPDLC communications within HELSINKI FIR shall insert the following in the respective items of their filed flight plan:
|
|
CPDLC clearance shall not be executed until the flight crew has sent a WILCO message in response to CPDLC clearance or instruction received. If uncertainty arises regarding a CPDLC clearance or instruction, voice communication shall always be used for clarification.
|
|
CPDLC exchanges within HELSINKI FIR may only be conducted when the aircraft is under the control and responsibility of Helsinki ACC.
|
|
The CPDLC service is not available within EFHK TMA nor within airspace blocks reserved by APP. The ATC will cancel the data transfer connection in these cases.
|
|
Pilots are requested to refrain from transmitting downlink messages when operating in the APP frequency even if the CPDLC connection has not been terminated.
|
|
5.5.1. DLIC Log-on
|
|
The CPDLC designator for HELSINKI FIR is EFIN. Log-on shall be initiated by the flight crew prior to entry into HELSINKI FIR. For aircraft departing from an aerodrome located within HELSINKI FIR, the log-on can be initiated on the ground. Log-on shall be initiated by the flight crew using their ICAO call sign as filed in the flight plan.
|
|
Following the completion of the Log-on procedure, the first EFIN ACC sector will perform a Start-CPDLC function, after the first radio contact with the aircraft.
|
|
Thereafter, the communication link (CPDLC) is available for sending / receiving messages within the HELSINKI FIR area.
|
|
5.5.2. ATC communications management (ACM)
|
|
When an aircraft is transferred by data link to an adjacent sector / ATS unit, the pilot shall acknowledge the instruction using data link WILCO message, and shall then contact the next sector / ATS unit by voice communication on the instructed channel.
|
|
Next ATS unit will inform current ATS service in initial radio contact, e.g. Helsinki Radar, Kajaani Information, Kuusamo TWR.
|
|
If the pilot is unable to comply with this CPDLC instruction, they shall revert to voice communication to inform ATC.
|
|
An aircraft operating within HELSINKI FIR that cannot be reached by the ATC on the appropriate voice channel may be issued one of the following pre-formatted free text CPDLC message:
|
|
CONTACT HELSINKI ACC ON VOICE CHANNEL
tai / or CONTACT HELSINKI ACC ON 121.500 |
|
No CPDLC response from the aircraft is expected and the flight crew shall contact Helsinki ACC through the appropriate voice channel.
|
|
5.5.3. ATC clearances and instructions (ACL)
|
|
Flight crew may request changes to flight levels (climb or descent) or clearance direct to a point on their route via CPDLC downlink messages. Any request by flight crew with voice shall be responded with voice by ATC.
|
|
Any clearance or instruction given by ATC with voice, shall be answered with voice.
|
|
In case to next ATS unit does not provide radar service, ATC shall send the following free text message before "CONTACT" message:
|
|
RADAR SERVICE TERMINATED
|
|
|
|
If the pilot wants to know reason for vectoring, or estimated remaining distance, he / she should ask it by voice communication.
|
|
If the ground system receives a message that is not supported, or constitutes an error to the technical rules for CPDLC communication, flight crew will receive an automatic reply indicating the nature of the error and, if applicable, required actions.
|
|
CPDLC service in HELSINKI FIR contains only the messages listed in section 5.5. All other messages will be replied to with an error message.
|
|
5.5.4. Free text ACL message
|
|
Use of free text ACL messages are not operationally supported. Free text messages composed by the flight crew will not be responded to by ATC and may result in an error message generated by the ground system.
|
|
5.5.5. CPDLC imposed silence
|
|
In order to contain the sector workload the ATC may require all stations or a specific flight to suspend sending CPDLC requests. For imposing or revoking CPDLC silence the following phrase, either as a voice or a CPDLC free text message shall be used:
|
|
|
5.5.6. ATC microphone check (AMC)
|
|
A "CHECK STUCK MICROPHONE" instruction may be sent by ATC in circumstances where an aircraft is inadvertently blocking a voice communication channel. If the "CHECK STUCK MICROPHONE" instruction relates to the RTF channel currently being used, the pilot shall check that their radio equipment is not causing the blockage.
|
|
5.5.7. Emergency and distress CPDLC messages
|
|
The following emergency / distress CPDLC messages are supported:
|
|
5.5.8. Voice interruption of CPDLC dialogue
|
|
To correct an unanswered CPDLC message, ATC shall initiate voice communication using the phrase:
|
|
DISREGARD CPDLC (viestityyppi) / (message type) MESSAGE, BREAK, REPLY WITH UNABLE
|
|
The pilot shall reply to the CPDLC message with an "UNABLE".
|
|
ATC will issue amended clearance by voice communication.
|
|
5.5.9. CPDLC failure
|
|
When alerted that CPDLC has failed, the controller will inform all stations under sector jurisdiction, using the following phrase:
|
|
ALL STATIONS, CPDLC FAILURE, [maa-aseman tunnus] / [identification of the calling station]
|
|
Some failures may result in termination of the existing data link connections with aircraft that are under control of a sector. In this case, it will not be possible for ATC to re-initiate dialogues via CPDLC unless the pilot re-initiates the data link logon process in order to re-establish data link connection. ATC will inform aircraft under their jurisdiction when CPDLC service is restored, using the following phrase:
|
|
ALL STATIONS, RESUME NORMAL CPDLC OPERATIONS
|
|
In case of a CPDLC failure, CPDLC clearances that have not yet been confirmed shall be repeated over voice communication and / or confirmed. If either the flight crew or ATC consider that CPDLC should not be used in the prevailing circumstances, CPDLC shall be suspended or terminated and the other party shall be informed by voice communication.
|
|
In case of a scheduled shutdown or an unexpected failure of the CPDLC system, ATC will instruct all aircraft equipped with data link to return to voice communication. In case of an onboard failure of CPDLC, the pilot shall return to voice communication and inform ATC.
|
|
5.5.10. Log-off
|
|
Log-off is automatic on leaving HELSINKI FIR or when landing at an aerodrome or airport within HELSINKI FIR. No pilot action is required.
|